-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix(otlptrace,otlpmetric): remove endpoint URL path cleaning #6710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(otlptrace,otlpmetric): remove endpoint URL path cleaning #6710
Conversation
This kind of indicates we should remove |
@mjq, ping 😉 See: #6710 (comment) |
b07ccf5
to
bb3fc07
Compare
@pellared Sorry for the delay! I incorporated @dmathieu's feedback re: removing the usage of I also realized I was changing generated files in the original commit - now the changes are made to the templates and applied with |
What about otlplog? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6710 +/- ##
=====================================
Coverage 82.3% 82.3%
=====================================
Files 263 263
Lines 24421 24421
=====================================
+ Hits 20099 20102 +3
+ Misses 3940 3937 -3
Partials 382 382
🚀 New features to boost your workflow:
|
c017642
to
8d9f666
Compare
I fixed the failing changelog check (bad automatic merge with
@pellared With this change |
Thanks. I noticed that |
Co-authored-by: Robert Pająk <pellared@hotmail.com>
@mjq, thank you very much for your contribution. |
When setting an explicit OTLP traces endpoint URL (via
otlptracehttp.WithEndpointURL
or theOTEL_EXPORTER_OTLP_TRACES_ENDPOINT
environment variable), any given trailing slash is stripped. This makes it impossible to export traces to an endpoint requiring a trailing slash. It also conflicts with the spec:This stripping happens due to the use of
path.Clean
inotlpconfig.cleanPath
. From thepath.Clean
docs:Other signals appear to use
path.Clean
and might therefore have the same bug, but I've only tested and fixed traces.Fixes #6709.